Adaptive power management in a battery powered system based on expected solar energy levels

ABSTRACT

A method and a management server located in the cloud, for enabling adaptive power management in a gateway system, are described. The management server receives, from the gateway system powered by a rechargeable battery that is coupled with a solar power source, a location measurement indicating the location of the gateway system at a first time. The management server determines a solar profile indicating a measure of the power expected to be generated by the solar power source at the location during an interval of time that occurs after the first time. The management server transmits the solar profile to the gateway system causing the gateway system to determine based on a current battery level of the rechargeable battery and the solar profile an optimal power usage plan for the gateway system and to operate according to the optimal power usage plan during the interval of time.

FIELD

Embodiments of the invention relate to the field of battery powermanagement, and more specifically, to enabling adaptive power managementin a system based on expected solar energy levels.

BACKGROUND

Battery-powered systems must commonly trade off system performance andbattery power management. Most systems alternate operation between alow-battery mode or a regular-battery mode. A battery power levelthreshold is predetermined and if the battery level of the system ismeasured to be below the predetermined threshold, the system enters alow-power state, in which performance is sacrificed to maintainsufficient battery levels. Alternatively, when the battery level of thesystem is measured to be above the predetermined threshold, then thesystem operates in a performant manner. The predetermined threshold istypically set statically and in a conservative manner particularly whenit is uncertain when battery power of the system may be replenished byan external power source.

Solar panels can be used to extend the operating life of battery-poweredsystems by replenishing the charge of the battery. Several powermanagement techniques change the performance characteristics of a systemdepending on which energy source (specifically, battery vs. solar) isprimarily used, exist.

Even though solar panels are currently used to extend the operating timeof existing battery-powered systems, such systems still rely on a doublepower mode of operations that is dependent on the type of power sourcethat is used to power the system (i.e., low power mode when the onlysource of power is the solar power source, and a normal/performant powermode when there is a different power source).

SUMMARY

One general aspect includes a method, in a management server located inthe cloud, of enabling adaptive power management in a gateway system,the method including: receiving, from the gateway system powered by arechargeable battery that is coupled with a solar power source, alocation reading indicating a location of the gateway system at a firsttime; determining a solar profile indicating a measure of power expectedto be generated by the solar power source at the location during aninterval of time that occurs after the first time; and transmitting thesolar profile to the gateway system causing the gateway system todetermine based on a current battery level of the rechargeable batteryand the solar profile an optimal power usage plan for the gateway systemand to operate according to the optimal power usage plan during theinterval of time.

One general aspect includes a management server device located in thecloud for enabling adaptive power management in a gateway system, themanagement server device including: a non-transitory computer readablestorage medium to store instructions; and a processor coupled with thenon-transitory computer readable storage medium to process the storedinstructions to receive, from the gateway system powered by arechargeable battery that is coupled with a solar power source, alocation reading indicating a location of the gateway system at a firsttime; determine a solar profile indicating a measure of power expectedto be generated by the solar power source at the location during aninterval of time that occurs after the first time; and transmit thesolar profile to the gateway system causing the gateway system todetermine based on a current battery level of the rechargeable batteryand the solar profile an optimal power usage plan for the gateway systemand to operate according to the optimal power usage plan during theinterval of time.

One general aspect includes a method, in gateway system powered by arechargeable battery that is coupled with a solar power source, ofenabling adaptive power management, the method including: transmitting alocation reading indicating a location of the gateway system at a firsttime; receiving from a management server a solar profile indicating ameasure of power expected to be generated at the location during aninterval of time that occurs after the first time by the solar powersource; determining based on a current battery level of the rechargeablebattery and the solar profile an optimal power usage plan for thegateway system; and operating according to the optimal power usage planduring the interval of time.

One general aspect includes a gateway system powered by a rechargeablebattery that is coupled with a solar power source, for enabling adaptivepower management, the gateway system including: a non-transitorycomputer readable storage medium to store instructions; and a processorcoupled with the non-transitory computer readable storage medium toprocess the stored instructions to: transmit a location readingindicating the location of the gateway system at a first time; receivefrom a management server a solar profile indicating a measure of powerexpected to be generated at the location during an interval of time thatoccurs after the first time by the solar power source; determine basedon a current battery level of the rechargeable battery and the solarprofile an optimal power usage plan for the gateway system; and operateaccording to the optimal power usage plan during the interval of time.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by referring to the followingdescription and accompanying drawings that are used to illustrateembodiments of the invention. In the drawings:

FIG. 1 illustrates a block diagram of an exemplary solar powered systemfor enabling adaptive power management in a battery powered gatewaysystem based on expected solar energy level, in accordance with someembodiments.

FIG. 2 illustrates an exemplary solar profile estimator for determininga solar profile indicating a measure of the power expected to begenerated by the solar power source at the location during an intervalof time, in accordance with some embodiments.

FIG. 3 illustrates an exemplary power consumption manager fordetermining an optimal power consumption plan, in accordance with someembodiments.

FIG. 4 illustrates a block diagram of a system for receiving powermeasures, in accordance with some embodiments.

FIG. 5 illustrates a flow diagram of exemplary operations for enablingadaptive power management in a battery powered gateway system based onexpected solar energy level, in accordance with some embodiments.

FIG. 6 illustrates a flow diagram of exemplary operations fordetermining a solar profile indicating a measure of the power expectedto be generated by the solar power source at the location during aninterval of time, in accordance with some embodiments.

FIG. 7 illustrates a flow diagram of exemplary operations for enablingadaptive power management in a battery powered gateway system based onexpected solar energy level, in accordance with some embodiments.

FIG. 8 illustrates a block diagram for an exemplary server managementthat can be used in some embodiments.

FIG. 9 illustrates a block diagram of an exemplary mobile asset that canbe used in some embodiments.

FIG. 10 illustrates a block diagram of an exemplary gateway system thatcan be used in some embodiments.

FIG. 11 illustrates a block diagram of an exemplary wireless sensingdevice that can be used in some embodiments.

DESCRIPTION OF EMBODIMENTS

In the following description, numerous specific details are set forth.However, it is understood that embodiments of the invention may bepracticed without these specific details. In other instances, well-knowncircuits, structures and techniques have not been shown in detail inorder not to obscure the understanding of this description. Those ofordinary skill in the art, with the included descriptions, will be ableto implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed. Throughout the following description similar referencenumerals have been used to denote similar elements such as components,features of a system and/or operations performed in a system or elementof the system, when applicable.

Bracketed text and blocks with dashed borders (e.g., large dashes, smalldashes, dot-dash, and dots) may be used herein to illustrate optionaloperations that add additional features to embodiments of the invention.However, such notation should not be taken to mean that these are theonly options or optional operations, and/or that blocks with solidborders are not optional in certain embodiments of the invention.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.“Coupled” is used to indicate that two or more elements, which may ormay not be in direct physical or electrical contact with each other,co-operate or interact with each other. “Connected” is used to indicatethe establishment of communication between two or more elements that arecoupled with each other.

According to some embodiments, a method and a management server locatedin the cloud, for enabling adaptive power management in a gatewaysystem, are described. In some embodiments, the management serverreceives, from the gateway system powered by a rechargeable battery thatis coupled with a solar power source, a location measurement indicatingthe location of the gateway system at a first time. The managementserver determines a solar profile indicating a measure of the powerexpected to be generated by the solar power source at the locationduring an interval of time that occurs after the first time. Themanagement server transmits the solar profile to the gateway systemcausing the gateway system to determine based on a current battery levelof the rechargeable battery and the solar profile an optimal power usageplan for the gateway system and to operate according to the optimalpower usage plan during the interval of time.

FIG. 1 illustrates a block diagram of an exemplary solar powered systemfor enabling adaptive power management in a battery powered gatewaysystem based on expected solar energy level, in accordance with someembodiments. The solar powered system includes a gateway system 110 thatis coupled with a solar power source 120, and a management server 140.In some embodiments, the gateway system can be located on a mobile asset(not illustrated) that has an unreliable access to an additional powersource (e.g., battery of a vehicle, etc.). In some embodiments, themobile asset is an unpowered vehicle (such as a trailer). In someembodiments, the mobile asset may be a powered system, however thegateway system mounted on the mobile asset may not have a permanent orconstant access to the power source of the mobile asset. In someembodiments, the gateway system is not plugged to the power source ofthe mobile asset, while in other embodiments the gateway system may havean intermittent connection to the power source of the mobile asset.

The mobile asset can be part of a fleet of mobile assets tracked by afleet management system that includes the gateway system and themanagement server. The mobile asset is typically located remotely fromthe management server 140 and may change location over a period of time.The mobile asset can be a trailer coupled with a tractor. The mobileasset can be a tractor, a tow truck, a semi-truck, a light or heavytruck or any other type of vehicle that is operative to be coupled withand pull a trailer. Alternatively, the mobile asset can be a car, a van,a bus, a specialized vehicle or any other type of vehicle.

The gateway system 110 is an electronic device and is operative to becoupled with the management server 140 through a Wide Area Network (WAN)130. The connection to the WAN 130 is a wireless connection (e.g., WiFi,cellular connection, etc.). In some embodiments, the gateway system 110and the management server 140 may be subject to an intermittentconnectivity with the WAN. The gateway system 110 is operative to recordor obtain data related to the vehicle on which it is mounted andtransmit the data to the management server 140. The gateway system 110transmits data indicative of a state of the vehicle. For example, thegateway system 110 may transmit location readings indicating thelocation of the mobile asset on which it is mounted. In someembodiments, the data further include additional sensor measurements forthe mobile asset (such as temperature, humidity, etc.). In someembodiments, the gateway system 110 is implemented as described infurther details with reference to FIG. 10. The gateway system 110 iscoupled with the solar power source 120. The solar power source convertsthe energy from sunlight into electricity. The solar power source 120may be part of the gateway system 110 and located within the samephysical device. In other embodiments, the solar power source 120 iscoupled with the gateway system 110 without being included in the samephysical device. The gateway system 110 includes a battery 102. Thebattery is a rechargeable battery that receives power from the solarpower source and is used to power the gateway system. In someembodiments, the gateway system 110 includes a location sensor 103. Thelocation sensor 103 is operative to determine the location of thegateway system 110. For example, the location sensor 103 can be a GlobalPositioning System (GPS) sensor that records GPS coordinates. In someembodiments, the location sensor can be located outside of the gatewaysystem 110 and coupled with the gateway system 110 through a wirelessprotocol (e.g., a short range wireless communication protocol). In someembodiments, the gateway system 110 also includes an adaptive powerusage manager 105 that is operative to determine an optimal power usageplan for the gateway system during an interval of time. Each of theelements of the gateway system 110 (except the battery 102) are powerconsuming components that operate with power received from the battery102. In some embodiments, the gateway system 110 may include additionalpower consuming elements 104 (e.g., sensor devices, communicationinterfaces, etc.).

The management server 140 is a cloud-based server operative to receivedata from one or more gateway systems (e.g., the gateway system 110).The data received from the gateway systems is used by the solar profileestimator 142 of the management server 140 to determine a solar profileindicating a measure of the power expected to be generated by the solarpower source 120 at the location of the gateway system 110 during aninterval of time. The solar profile causes the gateway system 110 toadapt its power consumption based on the solar profile. In someembodiments, the management server 140 includes an adaptive power usagemanager 105 that is to determine an optimal power usage plan for thegateway system 110 based on a current battery level of the battery 102.In some embodiments, the management server 140 is implemented asdescribed in further details with reference to FIG. 8.

In some embodiments, the gateway system 110 may be coupled with one ormore wireless sensing devices (not illustrated). The wireless sensingdevices (WSDs) are electronic devices that include one or more sensorsfor detecting physical events (e.g., temperature, humidity, barometricpressure, CO2 concentration, acceleration, pressure, sound, movement,etc.) and recording sensor measurements in response to the detection ofthese physical events. The wireless sensing devices can be smallelectronic devices that are attachable to an object for recording sensorinformation related to physical events related to the object (e.g.,recording changes in temperature, movement of an object (e.g., a doorbeing closed/opened), sudden accelerations of a vehicle, etc.). The WSDscan then store the sensor measurements related to physical eventsdetected over a period of time. The WSDs may record sensor measurementsat regular intervals of time (e.g., the WSDs may detect the temperatureof a room, or an object (e.g., refrigerator, food product), and recordcorresponding temperature measurements every N seconds or minutes). Thesensor measurements are stored in a non-transitory computer readablemedium of the WSDs. Each of the WSDs is operative to be coupled to agateway system (e.g., gateway system 110) and establish a communicationchannel to transfer the recorded sensor measurements. In someembodiments, each of the WSDs can connect to the gateway system througha wireless communication interface (e.g., Bluetooth Low Energy (BLE),WiFi). Thus, the WSDs are operative to detect a gateway system andnegotiate a connection to the gateway. In some embodiments, the WSDs areused to measure sensor measurements indicating current values of one ormore driving behavior parameter to be monitored for the vehicle during aroute. The WSDs can be implemented as described with reference to FIG.11.

At operation 1, the management server 140 receives, from the gatewaysystem 110, a location measurement indicating the location of thegateway system at a first time. The location reading is a sensormeasurement recorded by the location sensor 103. For example, thelocation sensor can be a Global Positioning System (GPS) sensor and thelocation reading includes GPS coordinates. The location readingindicates a location of the gateway system at a given time. In someembodiments, the location reading indicates a location of a mobile asseton which the gateway system 110 is mounted. In some embodiments, thegateway system 110 transmits several location readings that the locationof the mobile asset on which the gateway system 110 is mounted at one ormore times. For example, the gateway system 110 may transmit 10 locationreadings recorded in the last 5 minutes. The location readings indicatecurrent location of the gateway system 110. In some embodiments, eachlocation reading can include a longitude, latitude and an associatedtime (e.g., a timestamp). The time can indicate the time at which thelatitude and longitude were recorded by the location sensor;alternatively the timestamp can indicate the time at which the latitude,longitude are transmitted from the gateway system 110 or received by themanagement server 140.

At operation 4, the solar profile estimator 142 of the management server140 determines a solar profile indicating a measure of the powerexpected to be generated by the solar power source at the locationduring an interval of time that occurs after the first time. Theinterval of time can vary from few hours to few weeks. The solar profileis determined based on the location of the gateway system 110 asindicated by the location reading at the first time. In someembodiments, the solar profile may also be determined based on a solarindex of the location and/or the weather condition expected for thatlocation during the interval of time. For example, the management server140 may transmit, operation 2, the location of the gateway system 110 toone or more other servers (offering weather reports services 162, and/orsolar index information service 164) and obtain a solar index for thelocation (operation 3 a) and/or the weather condition (operation 3 b).In some embodiments, in addition to a solar profile, the managementserver 140 also transmits one or more certainty coefficients associatedwith this solar profile indicating a level of confidence in the solarprofile.

In some embodiments, the management server 140 transmits, at operation5, the solar profile to the gateway system 110. Upon receipt of thesolar profile, the gateway system 110 determines, at operation 6, basedon the solar profile and a current battery level of the rechargeablebattery an optimal power usage plan for the gateway system. In someembodiments, the gateway system 110 also uses the certainty coefficientsassociated with the solar profile to determine the optimal power usageplan. The gateway system then operates, at operation 7, according to theoptimal power usage plan during the interval of time.

In another embodiment, the management server 140, in addition toreceiving the location reading, receives a current battery level of thebattery 102. In this embodiment, in addition to determining the solarprofile, the management server 140 may also determine an optimal powerusage plan for the gateway system 110 (e.g., via the adaptive powerusage manager 105 that can optionally be located in the managementserver 140). In some embodiments, the management server 140 also usesthe certainty coefficients associated with the solar profile todetermine the optimal power usage plan. The optimal power usage planensures that the gateway system operates during the interval of timeabove a predetermined minimum energy threshold that guarantees areliable operation of the gateway system.

The embodiments described above enable adapting the operation modes ofthe gateway system 110 in a more dynamic way when compared toconventional solar powered system. Instead of relying only on the typeof power source that the gateway system is coupled with, or relying onlyon a current level of the battery 102, the gateway system 110 takes intoaccount the expected power to be generated by the solar power system 120in the future. The gateway system 110 operates according to an optimalpower usage plan for an interval of time, where the power usage plan isdetermined based on the power that is expected to be generated by thesolar power source during that interval of time. For example, thegateway system 110 may operate in a more efficient and performant modeeven if a battery level of the battery were below a predeterminedminimum threshold when the power expected to be generated during theinterval of time would allow a replenishment of the battery in a nearfuture. Alternatively, the gateway system 110 may operate in a moreconservative mode even if the battery level of the battery were abovethe predetermined threshold when the power expected to be generatedduring the interval of time would not allow a replenishment of thebattery in a near future. Thus, the gateway system 110 can use morepower in the present to take advantage of availability of power in thefuture.

The embodiments described herein can be used in a fleet tracking system.For example, gateway systems mounted on trailers enable a trailertracking system. In this scenario, the location sensor 103 recordslocation and telemetry data that is reported over a wireless connectionto a database stored on the management server 140 multiple times persecond. The gateway system 110 may obtain a solar profile from themanagement server 140 at a specified period (every few hours, every day,every week, etc.) to determine the optimal power usage plan for thelocation sensor. For example, the optimal power usage plan may cause adetermination of a number of location readings that are to be recordedby the location sensor during an interval of time (e.g., every second,every minute, every hour, etc.). As trailers move frequently, thepresent embodiments enable the gateway system of a given trailer toadapt to a solar energy expected to be received in a given location(even if the trailer has never been located in that location before).

The solution presented herein allows for easier installation of gatewaysystems on mobile assets as the gateway systems are no longer requiredto be coupled with an external power source (such as a battery of themobile asset or a vehicle on which the gateway system is mounted).Often, accessing power on a mobile asset is difficult and can causeproblems with keeping the mobile asset weather proof. In addition, sincein the solution presented herein the gateway system 110 is isolated fromthe power source of the mobile asset, the gateway system is not affectedby problems that occur with the power of the mobile asset and the mobileasset is also protected from the gateway system. Thus, keeping thegateway system isolated from the mobile asset's power prevents thegateway system from using too much of the mobile asset's power.

FIG. 2 illustrates an exemplary solar profile estimator for determininga solar profile indicating a measure of the power expected to begenerated by the solar power source at the location during an intervalof time, in accordance with some embodiments. The solar profileestimator 142 includes a power measures determiner 210 and a forecastingmodel applicator 230.

At operation 1, the power measures determiner 210 receives the locationreading indicating the location of the gateway system 110 at a firsttime. In some embodiments, the power measurements determiner 210 canalso include an interval of time for which a solar profile is to bedetermined. In other embodiments, the interval of time is predeterminedand is not received as an input. The interval of time can be anyinterval ranging from few minutes to few days. For example, the intervalof time can be a day. The length of the interval of time may affectcertainty coefficients that are determined for a solar profile. Theinterval of time can also be determined dynamically at the solar profileestimator 142. The interval of time can be determined based on a timethat the gateway system 110 is expected to remain at the location. Forexample, the management server 140 may include information about routesor stop locations scheduled for a mobile asset on which the gatewaysystem is mounted and the interval of time can be determined based onthis information. In other embodiments, the interval of time can bedetermined based on the power usage plan that according to which thegateway system 110 is operating.

The power measures determiner 210 determines one or more power measurespreviously recorded by one or more gateway systems. In some embodiments,the power measures determiner 210 includes recorded power measuresinformation 220. In some embodiments, the recorded power measuresinformation 220 is external to the solar profile estimator 142. In otherembodiments, the solar profile estimator 142 does not have access torecorded power measures information 220 at all, as no data is availableyet. The recorded power measures information 220 includes a set of powermeasures that were generated by one or more solar power sources coupledwith one or more gateway systems at various locations and times. Therecorded power measures information 220 can also include for each powermeasures, a time and date at which the measure was generated by arespective solar power source, and a location at which the power measurewas generated. The location can be a location reading from the locationsensor of the gateway system. In some embodiments, the recorded powermeasures information 220 is generated as described in further detailswith respect to FIGS. 3-4.

The power measures determiner 210 receives the location reading anddetermines based on the time associated with the location reading, a setof power measures. The power measures are selected from the set ofpreviously recorded power measures stored in the recorded power measuresinformation 220. In some embodiments, the selected power measuresinclude measures that were previously recorded within a predeterminedradius of the location of the gateway system 110 and within apredetermined time range of a start time of the interval of time forwhich the solar profile is to be determined. The predetermined radiuscan be any distance from the location readings for the gateway system110 (e.g., within 250 m, within 2 m, within 1 km). The predeterminedradius can be determined based on an analysis of the multiple powermeasures recorded. The analysis can determine the perimeter around agiven location for a gateway system for which power measures are similarfor a given time and day of the year. The predetermined time range canbe an interval of time for which the power measures are expected toremain substantially the same. For example, the predetermined time rangecan be few milliseconds to few seconds. Other examples of time range canbe used without departing from the scope of the present invention.

In some embodiments, the selected power measures include measures thatwere previously recorded at one or more locations that have anassociated solar index that is equivalent to a solar index of thelocation of the gateway system indicated by the location reading. Inthese embodiments, the selected power measures may have been recorded bygateway systems that were located at locations different from thelocation of the gateway system 110. These locations have a similar solarindex than the solar index for the location of the gateway system 110.For example, each one of the locations of the selected power measurescan have a solar index that is within a predetermined range from thesolar index of the location of the gateway system 110. In someembodiments, the selected power measures include measures that werepreviously recorded at one or more locations that have the same latitudeas the latitude of the location of the gateway system 110.

In some embodiments, the selected power measures can include only powermeasures that were previously recorded within a predetermined radius ofthe location of the gateway system 110 and within a predetermined timerange of a start time of the interval of time for which the solarprofile is to be determined, only measures previously recorded at one ormore locations that have an associated solar index that is equivalent toa solar index of the location of the gateway system, or a combination ofboth (previously recorded within the predetermined radius and thepredetermined time range or with a solar index that is equivalent). Insome embodiments, the power measures determiner 210 determines whetherthere are any power measures that were previously recorded within apredetermined radius of the location of the gateway system 110 andwithin the predetermined time range of the start time. If there are suchmeasures, the power measures determiner 210 selects those measures asthe selected power measures (operation 8). If there aren't any suchmeasures, the power measures determiner 210 may determine measurespreviously recorded at locations that have an associated solar indexthat is equivalent to a solar index of the location of the gatewaysystem as the selected power measures.

In some embodiments, the selected power measures were recorded at thesame time of day and the same time of the year as the time and day ofthe year at which the location of the gateway system 110 is received.For example, when the location of the start time of the time interval ison the first day of the first month of the year (January 1^(st)), theselected power measures were recorded on a first day of the first monthof a year.

In some embodiments, the recorded power measure information 220 includesadditional information about the solar power source and the recordedpower measures. For example, each power measure can be stored with oneor more of the following information: the type of solar power sourcethat generates the power measure (e.g., type of solar panel), age of thesolar power source (e.g., time since installation on the mobile asset,etc.), location of the power source on the mobile asset, orientation ofsolar power source, location of mobile asset relative to structures thatobscure the sun, the weather conditions at the location and at thattime, etc. In this embodiment, the selection of the power measures basedon the location of the gateway system 110 and the time is based on oneor more of these additional information. For example, the managementserver 140 may also have access to information about the location of thepower source 120 on the mobile asset or relative to the gateway system110, the type of solar power source used (if several types of solarpower source can be used), the age of the solar power source, theorientation of the solar power source 120, and/or the weather conditionsetc. and use this information to select from the recorded power measuresinformation 220 the selected power measures.

The result of the operation performed in the power measures determiner210 is the set of selected power measures (8). The forecasting modelapplication 230 uses the selected power measures to determine a solarprofile P_(inp)(t), indicating a measure of the power expected to begenerated by the solar power source 120 at the location of the gatewaysystem 110 during the interval of time T=[t0,t1] (or the power expectedto be input to the gateway system from the solar power source 120). Thesolar profile P_(inp)(t) includes one or more power measures expected tobe generated by the solar power source during the interval of time T. Insome embodiments, the solar profile is a discrete time series of powermeasures values during the interval T. In some embodiments, the solarprofile is a continuous function of time t over the interval T. Severalmodels can be used as the forecasting model applicator 230.Exponentially Weighted Moving Average (EWMA) forecast model, anautoregressive integrated moving average (ARIMA) model, or anautoregressive moving average (ARMA) model are exemplary models that canbe used to determine the solar profile.

In some embodiments, the forecasting model applicator 230 takes intoaccount the selected power measures, if available, the time of the day,a solar index (3 a) for the location of the gateway system 110, and/or aweather pattern (3 b) for the location of the gateway system 110. Insome embodiments, if there aren't any selected power measures, theforecasting model application 230 may query an external solar map forvalues for the location of the gateway system 110 for the past n daysand determines the solar profile for the gateway system 110.

In some embodiments, the forecasting model applicator 230 may assign tothe solar profile one or more certainty coefficients. In someembodiments, a single certainty coefficient is associated with the solarprofile for the entire interval of time. In other embodiments, differentcertainty coefficients are associated with the solar profile, eachcoefficient related to a different sub-interval of the interval of time.In some embodiments, a certainty coefficient is determined for each oneof the power measures expected to be generated by the solar power sourcethat form the solar profile. Each certainty coefficient can be a valuebetween [0, 1] that represents the confidence in the accuracy of thesolar profile during the corresponding sub-interval of time.

The certainty coefficients may depend on the type of power measuresselected at operation 8 and/or the date at which these power measureswere recorded. For example, the certainty coefficient of a solar profilethat is determined based on power measures recorded by the gatewaysystem 110 would be greater than a certainty coefficient of a solarprofile that is generated based on power measures from gateway systemsothers than the gateway system 110. In another example, the certaintycoefficient of a solar profile that is determined based on powermeasures recorded at the location of the gateway system 110 would begreater than a certainty coefficient of a solar profile that isgenerated based on power measures from different locations that have asolar index similar to the solar index of the location of the gatewaysystem 110. Further, the certainty coefficient may depend on thesub-interval to which it corresponds. For example, when the solarprofile is determined for an interval T=[t0, t1] including sub-intervals[t0, t2], [t2,t3] and [t3, t1], where t0<t2<t3<t1, the certaintycoefficients for the solar profile can be determined such that a highcertainty is assigned to the solar profile during the first timeinterval [t0, t2], then the certainty coefficient would be reduced forfurther out time intervals such as the second interval [t2,t3] and[t3,t1]. In a non-limiting example, the first certainty coefficient canbe 1 for the solar profile between [t0, t2] (e.g., t0 indicates acurrent time, t2 is 3 h after the current time); the second certaintycoefficient can be 0.9 for the solar profile between [t2, t3] (e.g., t3is 6 h after the current time); the third certainty coefficient can be0.8 for the solar profile between [t3, t1] (e.g., t1 is 9 h after thecurrent time). Other examples can be contemplated without departing fromthe scope of the present invention.

While in some embodiments, the solar profile can be determined based onpast power measurements recorded for the gateway system 110, in otherembodiments, the solar profile is determined based on past powermeasurements recorded by gateway systems others than the gateway system110. In some embodiments, the solar profile can be determined based onpast power measurements recorded for the gateway system 110 and othergateway systems. The embodiments described herein allow for predictionof an expected solar performance for the gateway system 110 at itscurrent location (i.e., the expected power to be generated by the powersource 120) even without information on prior power measures from thegateway system 110 at that location. The performance of the gatewaysystem 110 continually improves, as more data (e.g., power measures) isstored into the recorded power measures information 220, enabling thedetermination of more accurate solar profiles.

FIG. 3 illustrates an exemplary power consumption manager fordetermining an optimal power consumption plan, in accordance with someembodiments. In some embodiments, the adaptive power usage manager 105is located in the gateway system 110. In other embodiments, the adaptivepower usage manager 105 is located in the management server 140. Theadaptive power usage manager 105 is operative to determine an optimalpower consumption plan for the gateway system 110 based on the solarprofile for the interval of time. The adaptive power usage manager 105includes a power consumption controller 310, an optional power levelmonitor 320, and an optional power measures reporter 330.

The power consumption controller 310 receives the solar profile(operation 5) and a current battery level of the battery 102 (operation9) and determines (operation 6) an optimal power usage plan for thegateway system 110 for the interval of time [t0, t1].

The power usage plan includes power measures, P_(use)(t), which indicatethe amount of power to use at time t from the interval T=[t0, t1]by thegateway system 110. In some embodiments, the power usage plan may resultin charging the battery 102, which would increase the operating time ofthe gateway system 110 and enable power to be drawn from the battery ata later time. In some embodiments, the power usage plan may result indepleting the battery 102, and increasing the performance of the gatewaysystem 110.

Several approaches can be used to determine the power usage plan (i.e.,P_(use)(t) for t0<t <t1). In some embodiments, the power usage plan isdetermined based on: 1) the E_(t0), which is the battery level of thebattery 102 at time t0; 2) P_(min)(t), which is the minimum power neededby the device at an arbitrary time t; 3) E_(thresh)(t), which is the lowenergy threshold (i.e., if the battery level of battery 102 falls belowthis threshold, then the gateway system 110 reduces to the lowest powerconsumption operating state); and P_(inp)(t), which is the generatedsolar profile for the interval of time [t0, t1].

In one embodiment, a flat power use term C>0 is added to the minimumenergy usage, as per the equation below:

P _(use)(t)=P _(min)(t)+C . . .   (1)

C is maximized under the following minimum energy threshold constraint:

E _(t0)+∫_(t0) ^(t) [P _(inp)(t′)−P _(use)(t′)]dt′≥E _(thresh)(t) . . .  (2)

-   -   for all t0<t<t1        And P_(use)(t) is determined based on equation (1).

Several other approaches can be used for determining the power usageplan without departing from the scope of the present embodiments.

The optimal power usage plan ensures that the gateway system operatesduring the interval of time above the predetermined minimum energythreshold and that the power stored in the battery is used in a mostefficient manner taking into account the expected power to be generatedby the solar power system 120 in the future.

In some embodiments, the optimal power usage plan is used to determineconfiguration parameters of different components (e.g., sensors) of thegateway system (e.g., such as the frequency of measurements to berecorded, duration of the measurements, precision of the measurements,etc.), and/or to control power consumption of other aspects of thegateway system 110. For example, the optimal power usage plan is used todetermine the frequency, the duration and the precision of operation ofthe location sensor 103. In some embodiments, the power usage plan isalso used to determine how often and for how long the gateway system 110is to connect to the management server 140; how and when to connect toand/or pull data from other wireless devices (e.g., WSDs), as well asother functionalities of the gateway system 110.

In some embodiments, each component of the gateway system 110 canoperate in at least two energy modes of operations. For example, theenergy modes can include a low energy mode in which the energyconsumption of the component is lowered to a minimum, and a high energymode in which the energy consumption of the component is increased to amaximum. In some embodiments, one or more components of the gatewaysystem 110 may operate in at least one additional intermediary mode.

An exemplary gateway system 110 includes the location sensors with twoenergy modes (e.g., low energy mode yields location reading precision toa 250 meter radius, and a hi energy mode yields location readingprecision to a 10 meter radius); a cellular communication interface withtwo energy modes (e.g., low energy mode that causes the gateway system110 to request solar profiles from the management server 140 through thecellular communication interface once per day, and high energy modecauses the gateway system 110 to request solar profiles from themanagement server 140 through the cellular communication interface onceper hour; and a short range wireless communication protocol interfacewith two energy modes (e.g., a low energy mode that causes the gatewaysystem 110 to listens for packets from paired devices in 1 minutewindows at a predetermined interval, and a high energy mode that causesthe gateway system 110 to listens for packets from paired peripherals ina 5 minute window at the same predetermined interval).

The energy modes of operations of each component determine parameters ofoperations of each component. The power usage plan determined based on asolar profile for an interval of time [t0, t1] determines the mode ofoperation of each component. For example, when the power usage plan forthe interval [t0, t1] is greater than total power draw of locationsensor, cellular communication interface, and the short range wirelesscommunication protocol interface with all components set to high energymode (e.g. this could happen on a very sunny day), then, each of thesecomponents is set to operate in a high energy mode. This configurationscenario of the component of the gateway system 110, enable the locationsensor to return more precise location data, the cellular interface totransmit data at a higher frequency, and the short range interface tolisten to packets for a longer duration.

In another example, when the power usage plan for the interval [t2,t3]is less than total power draw of location sensor, cellularcommunication interface, and the short range wireless communicationprotocol interface with all components set to high energy mode (thissituation can occur at nighttime, for example), the energy mode ofoperation of at least one of the components is changed to a low energymode. For example, based on a given priority order, one or more of thelocation sensor, the cellular interface and the short-range interfaceare configured to operate in a low power mode. This may reduce theprecision of the location readings received from the location sensor103, reduce the frequency by which data is transmitted to the managementserver 140 through the cellular interface, and/or reduce the duration bywhich the gateway system 110 listens to paired devices through theshort-range interface.

The example above is presented for illustration purposes and is notintended to be limitative. Different scenarios, configurations modes,and energy modes of operations can be contemplated without departingfrom the scope of the present embodiments. The example above illustratethe adaptability of the power consumption of the gateway system 110based on the solar profile that is determined for a given interval oftime.

Referring back to FIG. 3, the adaptive power usage manager 105 can alsoinclude a power level monitor 320. The power level monitor 320 isoperative to receive the solar profile and the current power levelgenerated by the solar power source, operation 10, and determine whetherthe current power level generated is less than the expected power levelindicated by the solar profile at a given time t. When the current powerlevel is less than the expected power level, the power level monitor 320may transmit an alert to the management server 140. The alert enablesthe system owner/administrator to perform maintenance on the deployedsystems by identifying solar power sources with unexpected power levelproduction.

The adaptive power usage manager 105 also includes a power measuresreporter 330. The power measures reporter 330 receives, operation 10,the power level generated by the solar power source at a given time t,the location reading (operation 12) indicating the location the gatewaysystem 110 at the time t, and transmits them (operation 13) to themanagement server 140. The management server 140 records the receivedinformation as a power measure in the recorded power measuresinformation 220.

In some embodiments, the transmission of the power measures is performedat a regular interval of time (e.g., once a second, once a minute, oncean hour, once a day, etc.). The frequency of the transmission of thepower measures can depend on the energy mode on which the components ofthe gateway system 110 are operating. For example, when a communicationinterface that couples the gateway system 110 with the management server140 is running on a low energy mode, the transmission of the powermeasures may be performed less frequently than when the communicationinterface runs on a high energy mode. In some embodiments, the gatewaysystem 110 does not transmit the power measures.

In some embodiments, the management server 140 continuously receivespower measures from multiple gateway systems at various locations andpopulates the recorded power measures information 220. FIG. 4illustrates a block diagram of a system for receiving power measures, inaccordance with some embodiments. Each of the gateway systems 110A-Zincludes a respective power measures reporter 330A-Z. Each of the powermeasures reporter 330A-Z is operative to transmit a power measuregenerated by the solar power source at a given time t and an associatedlocation reading for that time (e.g., latitudes, longitudes, time t).The management server 140 receives power measures from each gatewaysystem 110 that are mounted on mobile assets part of a fleet of assets.The power measures may be recorded at different times of the day,different locations, and transmitted at various frequencies. The powermeasures are added (operation 14) by the management server 140 torecorded power measures information 220. Obtaining the power measuresfrom multiple gateway devices, enable the management server to determinea solar profile for the gateway system 110 at the location even if thegateway system has never been located in that location before.

The operations in the flow diagrams of FIGS. 5-7 will be described withreference to the exemplary embodiments of FIGS. 1-4. However, it shouldbe understood that the operations of the flow diagrams can be performedby embodiments of the invention other than those discussed withreference to the other figures, and the embodiments of the inventiondiscussed with reference to these other figures can perform operationsdifferent than those discussed with reference to the flow diagrams.

FIG. 5 illustrates a flow diagram of exemplary operations for enablingadaptive power management in a battery powered gateway system based onexpected solar energy level, in accordance with some embodiments. Insome embodiments, the operations of FIG. 5 are performed by themanagement server 140 when coupled with the gateway system 110. In someembodiments, these operations are performed at a regular interval oftime (e.g., once an hour, once a day, etc.). The frequency of theoperations can depend on the energy mode on which the components of thegateway system 110 are operating. For example, when a communicationinterface that couples the gateway system 110 with the management server140 is running on a low energy mode, the operations may be performed ata smaller frequency than when the communication interface runs on a highenergy mode. In some embodiments, the operations of FIG. 5 can betriggered by an event within the gateway system 110. For example, adetection that a solar profile received indicates an expected power tobe generated by the solar power source 120 at a time t greater than theactual power generated by the solar power source 120 at that time t, cancause the gateway system 110 to request a new solar profile andpotentially update its power usage plan.

At operation 510, the management server 140 receives, from the gatewaysystem 110 powered by a rechargeable battery 102 that is coupled with asolar power source 120, a location reading indicating a location of thegateway system at a first time. At operation 520, the management server140 determines a solar profile indicating a measure of the powerexpected to be generated by the solar power source at the locationduring an interval of time that occurs after the first time, andtransmits, at operation 530, the solar profile to the gateway system 110causing the gateway system to determine based on a current battery levelof the rechargeable battery and the solar profile an optimal power usageplan for the gateway system and to operate according to the optimalpower usage plan during the interval of time.

FIG. 6 illustrates a flow diagram of exemplary operations fordetermining a solar profile indicating a measure of the power expectedto be generated by the solar power source at the location during aninterval of time, in accordance with some embodiments. At operation 610,the management server 140 determines, based on the location of thegateway system, one or more power measures previously recorded. In someembodiments, the power measures previously recorded were recorded, 612,within a predetermined radius of the location of the gateway system 110and within a predetermined time range of a start time of the interval oftime. In some embodiments, the power measures previously recorded wererecorded, 614, at one or more locations that have an associated solarindex that is equivalent to a solar index of the location of the gatewaysystem. In some embodiments, the locations with an equivalent solarindex are at a same latitude as the location of the gateway system 110.In some embodiments, the power measures may include power measuresrecorded within a predetermined radius of the location of the gatewaysystem 110 and within a predetermined time range of a start time andpower measures with an associated solar index that is equivalent to asolar index of the location of the gateway system.

The flow then moves to operation 620, at which the management server 140determines, based on a forecasting model and the one or more powermeasures previously recorded, power measures expected to be generated bythe solar power source during the interval of time. In some embodiments,the flow of operations further moves to optional operation 630, atwhich, the management server 140 determines for each one of the one ormore power measures expected to be generated by the solar power sourcean associated certainty coefficient.

FIG. 7 illustrates a flow diagram of exemplary operations for enablingadaptive power management in a battery powered gateway system based onexpected solar energy level, in accordance with some embodiments. Theoperations of FIG. 7 are performed in a gateway system (e.g., gatewaysystem 110). In some embodiments, these operations are performed at aregular interval of time (e.g., once an hour, once a day, etc.). Thefrequency of the operations can depend on the energy mode on which thecomponents of the gateway system 110 are operating. For example, when acommunication interface that couples the gateway system 110 with themanagement server 140 is running on a low energy mode, the operationsmay be performed at a smaller frequency than when the communicationinterface runs on a high energy mode. In some embodiments, theoperations of FIG. 7 can be triggered by an event within the gatewaysystem 110. For example, a detection that a solar profile receivedindicates an expected power to be generated by the solar power source120 at a time t greater than the actual power generated by the solarpower source 120 at that time t, can cause the gateway system 110 torequest a new solar profile and potentially update its power usage plan.

At operation 710, the gateway system 110 transmits a location readingindicating the location of the gateway system at a first time. Atoperation 720, the gateway system 110 receives from a management server(e.g., management server 140) a solar profile indicating a measure ofthe power expected to be generated at the location during an interval oftime that occurs after the first time by the solar power source. Atoperation 730, the gateway system 110 determines based on a currentbattery level of the rechargeable battery and the solar profile anoptimal power usage plan for the gateway system. Flow moves to operation740, at which the gateway system 110 operates according to the optimalpower usage plan during the interval of time (e.g., [t0, t1]). In someembodiments, the optimal power usage plan ensures that the gatewaysystem operates during the interval of time above a predeterminedminimum energy threshold. The optimal power usage plan ensures that thepower stored in the battery of the gateway system is used in a mostefficient manner taking into account the expected power to be generatedby the solar power system 120 in the future. In some embodiments, theoptimal power usage plan causes the battery of the gateway system to becharged while maintaining operation of the gateway system. In otherembodiments, the optimal power usage plan causes the battery of thegateway system to be depleted. While in some embodiments, the gatewaysystem 110 is further to perform operations 750 and 760, in otherembodiments, these operations are skipped.

Architecture

The gateway systems and the management server described with referenceto FIGS. 1-7 are electronic devices. An electronic device stores andtransmits (internally and/or with other electronic devices over anetwork) code (which is composed of software instructions and which issometimes referred to as computer program code or a computer program)and/or data using machine-readable media (also called computer-readablemedia), such as machine-readable storage media (e.g., magnetic disks,optical disks, read only memory (ROM), flash memory devices, phasechange memory) and machine-readable transmission media (also called acarrier) (e.g., electrical, optical, radio, acoustical or other form ofpropagated signals—such as carrier waves, infrared signals). Thus, anelectronic device (e.g., a computer) includes hardware and software,such as a set of one or more processors coupled to one or moremachine-readable storage media to store code for execution on the set ofprocessors and/or to store data. For instance, an electronic device mayinclude non-volatile memory containing the code since the non-volatilememory can persist the code even when the electronic device is turnedoff, and while the electronic device is turned on that part of the codethat is to be executed by the processor(s) of that electronic device iscopied from the slower non-volatile memory into volatile memory (e.g.,dynamic random access memory (DRAM), static random access memory (SRAM))of that electronic device. Typical electronic devices also include a setor one or more physical network interface(s) to establish networkconnections (to transmit and/or receive code and/or data usingpropagating signals) with other electronic devices. One or more parts ofan embodiment of the invention may be implemented using differentcombinations of software, firmware, and/or hardware.

FIG. 8 illustrates a block diagram for an exemplary server managementthat can be used in some embodiments. Management server 140 may be a Webor cloud server, or a cluster of servers, running on server hardware. Inone embodiment, the management server 140 works for both single andmulti-tenant installations, meaning that multiple organizations withdifferent administrators may have wireless sensing devices and gatewaysystems managed by the same management server.

According to one embodiment, management server 140 is implemented on aserver device 830, which includes server hardware 805. Server hardware805 includes network communication interfaces 860 coupled with acomputer readable storage medium 810. The computer readable storagemedium 810 includes solar profile estimator code 812 which when executedby the processor(s) 815 cause the management server 140 to perform theoperations described with reference to FIGS. 1-7. The computer readablestorage medium 810 includes an optional sensor measurements database 844(including sensor measurements obtained from one or more sensors coupledwith a gateway system), an optional organizations database 850(including information regarding the organizations to which the gatewaysystems, or the mobile assets belong); a gateway systems database 846(including information regarding the gateway systems), a wirelesssensing device database 848 (including information regarding the WSDs).In some embodiments, the computer readable storage medium 810 alsostores the recorded power measures 220.

While one embodiment does not implement virtualization, alternativeembodiments may use different forms of virtualization—represented by avirtualization layer 820. In these embodiments, the management server140 and the hardware that executes it form a virtual management server,which is a software instance of the modules stored on the computerreadable storage medium 810.

FIG. 9 illustrates a block diagram of an exemplary vehicle that can beused in some embodiments. Mobile asset 900 includes a gateway system 110coupled with a solar power source 120. In some embodiments, the mobileasset may also include a computing device 904. The computing device isan electronic device installed by the manufacturer of the mobile asset.The mobile asset 900 may include one or more sensors 902 and a battery906 that can be installed by the manufacturer of the vehicle oraftermarket sensors. The sensors are electronic devices operative torecord and transmit data through the gateway system 110 towards amanagement server 140.

FIG. 10 illustrates a block diagram of an exemplary gateway system thatcan be used in some embodiments. Gateway system 110 includes one or moreprocessors 1005 and connected system components (e.g., multipleconnected chips). The gateway system 110 includes computer readablestorage medium 1010, which is coupled to the processor(s) 1005. Thecomputer readable storage medium 1010 may be used for storing data,metadata, and programs for execution by the processor(s) 1005. Forexample, the depicted computer readable storage medium 1010 may storeadaptive power usage manager code that, when executed by theprocessor(s) 1005, in combination with the hardware component powermanager 1008 causes the gateway system 110 to perform operations asdescribed with reference to the embodiments of FIGS. 1-7.

The gateway system 110 also includes one or more sensors used to recordsensor measurements in response to physical events. For example, thegateway system 110 may include a location sensor (such as a GPS sensor)103 for recording location readings to indicate the location of thegateway system. The gateway system 110 may include one or more otherpower consuming elements 104 (e.g., other sensors (e.g., anaccelerometer)).

The gateway system 110 also includes one or more communicationinterfaces 1006, which are provided to allow a user to provide input to,receive output from, and otherwise transfer data to and from the gatewaysystem. Exemplary Input/Output devices and interfaces 1006 include wiredand wireless transceivers, such as Joint Test Action Group (JTAG)transceiver, a Bluetooth Low Energy (LE) transceiver, an IEEE 802.11transceiver, an infrared transceiver, a wireless cellular telephonytransceiver (e.g., 2G, 3G, 4G), or another wireless protocol to connectthe gateway system 110 with another device, external component, or anetwork and receive stored instructions, data, tokens, etc. The gatewaysystem also includes a battery 102. The battery is a rechargeablebattery coupled with a solar power source. In some embodiments, thesolar power source can be part of the gateway system 110. In someembodiments, some components of the gateway system 110 can be externalto the gateway system (e.g., the battery, can be an additional batterycoupled with the solar power source and operative to transfer power tothe gateway system 110). It will be appreciated that one or more busesmay be used to interconnect the various components shown in FIG. 10.

FIG. 11 illustrates a block diagram of an exemplary wireless sensingdevice that can be used in some embodiments. Wireless sensing device1100 includes one or more processors 1105 and connected systemcomponents (e.g., multiple connected chips). The wireless sensing device1100 includes computer readable storage medium 1110, which is coupled tothe processor(s) 1105. The computer readable storage medium 1110 may beused for storing data, metadata, and programs for execution by theprocessor(s) 1105. For example, the depicted computer readable storagemedium 1110 may store sensor measurement management module 1111 that,when executed by the processor(s) 1105, causes the WSD 1100 to offloaddata to a gateway system to be transmitted to the management server.

In some embodiments, the sensor measurement management module 1111 maycause the WSD to adapt a rate at which it generates sensor measurementsbased on feedback received from the gateway system 110 and the powerusage plan of the gateway system 110.

The WSD 1100 also includes one or more sensor(s) to detect physicalevents and store sensor measurements in the computer readable storagemedium 1110 in response to the detection of the physical events. In someexemplary embodiments, the one or more sensor(s) include at least one ofa temperature sensor, an ambient light sensor, an accelerometer, and agyroscope, etc.

The WSD 1100 also includes one or more communication interfaces 1106,which are provided to allow a user to provide input to, receive outputfrom, and otherwise transfer data to and from the WSD. ExemplaryInput/Output devices and interfaces 1106 include wired and wirelesstransceivers, such as Joint Test Action Group (JTAG) transceiver, aBluetooth Low Energy (LE) transceiver, an IEEE 802.11 transceiver, aninfrared transceiver, a wireless cellular telephony transceiver (e.g.,2G, 3G, 4G), or another wireless protocol to connect the WSD 1100 withanother device, external component, or a network and receive storedinstructions, data, tokens, etc. It will be appreciated that one or morebuses may be used to interconnect the various components shown in FIG.11.

It will be appreciated that additional components, not shown, may alsobe part of the management device 140, the mobile asset 900, the gatewaysystem 110, or the WSD 1100 and, in certain embodiments, fewercomponents than that shown in FIGS. 8-11 may also be used.

While some components of the gateway system, or the management serverare illustrated as code stored on the computer readable storage medium,in other embodiments the modules may be implemented in hardware or in acombination of hardware and software. While the flow diagrams in thefigures show a particular order of operations performed by certainembodiments of the invention, it should be understood that such order isexemplary (e.g., alternative embodiments may perform the operations in adifferent order, combine certain operations, overlap certain operations,etc.).

Additionally, while the invention has been described in terms of severalembodiments, those skilled in the art will recognize that the inventionis not limited to the embodiments described, can be practiced withmodification and alteration within the spirit and scope of the appendedclaims. The description is thus to be regarded as illustrative insteadof limiting.

1. A method, in a management server located in the cloud, of enablingadaptive power management in a gateway system that is mounted on amobile asset, the method comprising: receiving, from the gateway systempowered by a rechargeable battery that is coupled with a solar powersource, a location reading indicating a location of the gateway systemat a first time; determining a solar profile indicating a measure ofpower expected to be generated by the solar power source at the locationof the gateway system during an interval of time that occurs after thefirst time; and transmitting the solar profile to the gateway systemcausing the gateway system to determine based on a current battery levelof the rechargeable battery and the solar profile an optimal power usageplan for the gateway system and causing the gateway system to use theoptimal power usage plan for determination of configuration parametersof one or more components of the gateway system, and wherein theconfiguration parameters include at least one of frequency ofmeasurements to be recorded by at least one of the components of thegateway system, duration of the measurements, and precision of themeasurements.
 2. The method of claim 1, wherein determining a solarprofile includes: determining, based on the location of the gatewaysystem, one or more power measures previously recorded; and determining,based on a forecasting model and the one or more power measurespreviously recorded, one or more power measures expected to be generatedby the solar power source during the interval of time.
 3. The method ofclaim 2, wherein determining a solar profile further includes:determining for each one of the one or more power measures expected tobe generated by the solar power source an associated certaintycoefficient.
 4. The method of claim 2, wherein the one or more powermeasures previously recorded were recorded within a predetermined radiusof the location of the gateway system and within a predetermined timerange of a start time of the interval of time.
 5. The method of claim 2,wherein the one or more power measures previously recorded were recordedat one or more locations that have an associated solar index that isequivalent to a solar index of the location of the gateway system. 6.The method of claim 1, wherein the mobile asset has an unreliable accessto a power source.
 7. A management server device located in the cloudfor enabling adaptive power management in a gateway system that ismounted on a mobile asset, the management server device comprising: anon-transitory computer readable storage medium to store instructions;and a processor coupled with the non-transitory computer readablestorage medium to process the stored instructions to: receive, from thegateway system powered by a rechargeable battery that is coupled with asolar power source, a location reading indicating a location of thegateway system at a first time, determine a solar profile indicating ameasure of power expected to be generated by the solar power source atthe location of the gateway system during an interval of time thatoccurs after the first time, and transmit the solar profile to thegateway system causing the gateway system to determine based on acurrent battery level of the rechargeable battery and the solar profilean optimal power usage plan for the gateway system and causing thegateway system to use the optimal power usage plan for determination ofconfiguration parameters of one or more components of the gatewaysystem, and wherein the configuration parameters include at least one offrequency of measurements to be recorded by at least one of thecomponents of the gateway system, duration of the measurements, andprecision of the measurements.
 8. The management server device of claim7, wherein to determine a solar profile includes to: determine, based onthe location of the gateway system, one or more power measurespreviously recorded; and determine, based on a forecasting model and theone or more power measures previously recorded, one or more powermeasures expected to be generated by the solar power source during theinterval of time.
 9. The management server device of claim 8, wherein todetermine a solar profile further includes to: determine for each one ofthe one or more power measures expected to be generated by the solarpower source an associated certainty coefficient.
 10. The managementserver device of claim 8, wherein the one or more power measurespreviously recorded were recorded within a predetermined radius of thelocation of the gateway system and within a predetermined time range ofa start time of the interval of time.
 11. The management server deviceof claim 8, wherein the one or more power measures previously recordedwere recorded at one or more locations that have an associated solarindex that is equivalent to a solar index of the location of the gatewaysystem.
 12. The management server device of claim 7, wherein the mobileasset has an unreliable access to a power source.
 13. A method, ingateway system powered by a rechargeable battery that is coupled with asolar power source, of enabling adaptive power management, the methodcomprising: transmitting a location reading indicating a location of thegateway system at a first time; receiving from a management server asolar profile indicating a measure of power expected to be generated atthe location during an interval of time that occurs after the first timeby the solar power source; determining based on a current battery levelof the rechargeable battery and the solar profile an optimal power usageplan for the gateway system; and operating according to the optimalpower usage plan during the interval of time.
 14. The method of claim13, wherein the solar profile includes, one or more power measuresexpected to be generated by the solar power source during the intervalof time.
 15. The method of claim 13, wherein the optimal power usageplan ensures that the gateway system operates during the interval oftime above a predetermined minimum energy threshold.
 16. The method ofclaim 13, wherein the optimal power usage plan causes the battery of thegateway system to be charged while maintaining operation of the gatewaysystem.
 17. The method of claim 13, wherein operating according to theoptimal power usage plan during the interval of time includes modifyinga frequency for reporting one or more sensor measurements from thegateway system to the management server, wherein the sensor measurementsinclude at least a location reading indicating the location of thegateway system.
 18. The method of claim 13, wherein the method furthercomprises: determining whether a level of power generated by the solarpower source at a given time during the time interval is less than anexpected power measure at the given time determined based on the solarprofile; and responsive to determining that the level of power generatedby the solar power source is less than an expected power measure at thegiven time, triggering an alert indicating that causes the gatewaysystem to operate based on an updated power usage plan.
 19. The methodof claim 13 further comprising: transmitting, to the management server,one or more power measures generated by the solar power source at agiven location and a given time.
 20. A gateway system powered by arechargeable battery that is coupled with a solar power source, forenabling adaptive power management, the gateway system comprising: anon-transitory computer readable storage medium to store instructions;and a processor coupled with the non-transitory computer readablestorage medium to process the stored instructions to: transmit alocation reading indicating the location of the gateway system at afirst time; receive from a management server a solar profile indicatinga measure of power expected to be generated at the location during aninterval of time that occurs after the first time by the solar powersource; determine based on a current battery level of the rechargeablebattery and the solar profile an optimal power usage plan for thegateway system; and operate according to the optimal power usage planduring the interval of time.
 21. The gateway system of claim 20, whereinthe solar profile includes, one or more power measures expected to begenerated by the solar power source during the interval of time.
 22. Thegateway system of claim 20, wherein the optimal power usage plan ensuresthat the gateway system operates during the interval of time above apredetermined minimum energy threshold.
 23. The gateway system of claim20, wherein the optimal power usage plan causes the battery of thegateway system to be charged while maintaining operation of the gatewaysystem.
 24. The gateway system of claim 20, wherein to operate accordingto the optimal power usage plan during the interval of time includes tomodify a frequency for reporting one or more sensor measurements fromthe gateway system to the management server, wherein the sensormeasurements include at least a location reading indicating the locationof the gateway system.
 25. The gateway system of claim 20, wherein theprocessor is further to: determine whether a level of power generated bythe solar power source at a given time during the time interval is lessthan an expected power measure at the given time determined based on thesolar profile; and responsive to determining that the level of powergenerated by the solar power source is less than an expected powermeasure at the given time, trigger an alert indicating that causes thegateway system to operate based on an updated power usage plan.
 26. Thegateway system of claim 20, wherein the processor is further to:transmit, to the management server, one or more power measures generatedby the solar power source at a given location and a given time.